docs: record issue 9 roadmap status and reset G2 evidence to candidate - #1

Summary

• Add docs/2026-08-30-issue-9-roadmap-status.md: one dated status/decision record for Roadmap: establish Psyche as OpenCoven's canonical orchestration protocol OpenCoven/psyche#9, in the repo's record location (docs/, where G2-EVIDENCE.md already lives). It records what exists on main at 1e47b40 (contract foundation, CI, retained evidence — with links and dates), the state of each 90-day phase and workstream outcome (Land Psyche repository and agent-readiness foundation OpenCoven/psyche#10–Establish Psyche security, release, support, and governance readiness OpenCoven/psyche#14 plus Scope retained G2 evidence to the attested contract surface OpenCoven/psyche#17/P1: Define the Psyche adapter for automation-triggered orchestration without owning schedules OpenCoven/psyche#18), a verdict against all nine global acceptance criteria, and the remaining critical path. Facts only.
• Reset docs/G2-EVIDENCE.md from passed to the exact candidate placeholder state. The retained passed record pins tested commit f4f242f…, a dangling squash of fix: accept canonical G2 merge push shape OpenCoven/psyche#8 that is not an ancestor of main, so scripts/check-g2-evidence.py rejects every content PR before it starts — observed directly on PR Establish Psyche roadmap and agent-readiness foundation OpenCoven/psyche#15, which fails the "G2 evidence relationships" step on ubuntu, macOS, and Windows (run 32956215259) while its other four checks are green. Candidate status is this repo's established rhythm for content PRs (e12b059 "docs: reset G2 evidence after hardening" is the precedent): the checker skips remote attestation for candidate, and a docs-only follow-up PR re-attests passed against the merged squash commit. No contracts, tests, workflow, manifest, or fixtures are touched. Draft PR Scope retained G2 evidence to the attested contract surface OpenCoven/psyche#17 proposes the structural (scope-policy) alternative and remains the cleaner long-term fix; this reset is the minimal unblocking step consistent with repo convention.

No protocol, storage, adapter, or CI-workflow behavior is changed by this PR.

Issue

Refs OpenCoven#9

Test plan

• Local: ported the checker's validate_evidence candidate contract to a throwaway Node script — 32 criteria match the command SHA-256 allowlist with exact-filter syntax, 5 Coven source rows byte-identical, candidate placeholders exact, manifest↔matrix atomic commands agree (78 commands). (Script not committed; python3 is unavailable in this environment.)
• Local: npm --prefix packages/psyche-npm test — 16/16 pass.
• Local: npm pack ./packages/psyche-npm --dry-run — 5 files, matches CI expectation.
• CI: Rust checks (fmt/clippy/tests are docs-only changes; G2 evidence step expected green with candidate evidence) — deferred to CI.
• CI: Dependency audit, Secret guard, npm distribution legs — deferred to CI (Rust toolchain and cargo-deny/gitleaks are not available in this environment).

Vehicle note: opened in the fork CompleteDotTech/psyche as the CI vehicle — this token cannot write to OpenCoven/psyche. Re-target upstream once write access is restored. Refs OpenCoven#9.

CI note (2026-08-30): the fork vehicle is checkless — REST shows 0 registered workflows, 0 workflow runs, and 0 check runs for head de33cd5 after the standard ~10-minute wait (upstream OpenCoven/psyche runs the real CI in .github/workflows/ci.yml; those checks cannot execute here until this PR is re-targeted upstream). The deferred checks in the test plan above therefore remain deferred rather than green.